NACK-Oriented Reliable Multicast - définition. Qu'est-ce que NACK-Oriented Reliable Multicast
Diclib.com
Dictionnaire ChatGPT
Entrez un mot ou une phrase dans n'importe quelle langue 👆
Langue:

Traduction et analyse de mots par intelligence artificielle ChatGPT

Sur cette page, vous pouvez obtenir une analyse détaillée d'un mot ou d'une phrase, réalisée à l'aide de la meilleure technologie d'intelligence artificielle à ce jour:

  • comment le mot est utilisé
  • fréquence d'utilisation
  • il est utilisé plus souvent dans le discours oral ou écrit
  • options de traduction de mots
  • exemples d'utilisation (plusieurs phrases avec traduction)
  • étymologie

Qu'est-ce (qui) est NACK-Oriented Reliable Multicast - définition


NACK-Oriented Reliable Multicast         
AN INTERNET TRANSPORT-LAYER PROTOCOL USED TO TRANSMIT DATA RELIABLY IN MULTICAST GROUPS
User:RichardWJones/sandbox; Draft:NACK-Oriented Reliable Multicast
NACK-Oriented Reliable Multicast (NORM) is a transport layer Internet protocol designed to provide reliable transport in multicast groups in data networks. It is formally defined by the Internet Engineering Task Force (IETF) in Request for Comments (RFC) 5740, which was published in November 2009.
Reliable Replacement Warhead         
AERIAL BOMB
Reliable replacement warhead; Reliable Replacement Warhead Program; RRW; RRW1; RRW2
The Reliable Replacement Warhead (RRW) was a proposed new American nuclear warhead design and bomb family that was intended to be simple, reliable and to provide a long-lasting, low-maintenance future nuclear force for the United States. Initiated by the United States Congress in 2004, it became a centerpiece of the plans of the National Nuclear Security Administration (NNSA) to remake the nuclear weapons complex.
Reliable Server Pooling         
Reliable Server Pooling (RSerPool) is a computer protocol framework for management of and access to multiple, coordinated (pooled) servers. RSerPool is an IETF standard, which has been developed by the IETF RSerPool Working GroupRSerPool and documented in RFC 5351, RFC 5352, RFC 5353, RFC 5354, RFC 5355 and RFC 5356.